Config.dat File
The Config.dat file is an initialization file that contains settings applicable to all PPM products or to a specific product.
- In the registry: Cobra looks for the folder of Config.dat file in the
<HKEY_CURRENT_USER>\Software\Deltek\Cobra\<Cobra version>\ProgramFolder key in the registry. If
<HKEY_CURRENT_USER>\Software\Deltek\Cobra\<Cobra version>\ConfigDat key exists in the registry, Cobra uses that as the filename of Config.dat. If the key does not exist, Cobra uses Config.dat as the filename.
When Cobra reaches to the point that it prompts the user for the Config.dat file, Cobra saves the folder on the registry. If the user selected a different filename, Cobra also saves the filename on the registry.
- From the Cobra folder
- Prompt user for location
- Location of the Datasources.dat file
-
Initial default data source
Example
{SYSTEM]
DATASOURCES=C:\ConfigFiles\Datasources.dat
DATASOURCE=COBRA
In this example, the Datasources.dat file is located in C:\ConfigFiles directory. The initial default data source is COBRA, which will be initially selected in the Cobra Login dialog box.
You can pass command line parameters to the API to specify the location of the IdeaBlade.Ibconfig and Config.dat files.
datasource:<name of datasource>
"C:\Program Files\Deltek\Cobra\Cobra.API.exe" datasource:DB2
You must add quotes around the folder name. If you omit the quotes in the /datasource parameter, the application uses the IdeaBlade.Ibconfig or Config.dat file in the application’s folder. The location of the Datasources.dat file is defined inside the Config.dat file. If the location of the Datasources.dat file is not specified in the Config.dat file, you must move the Datasources.dat file within the same folder where the Config.dat file is located.
In an n-tier environment, you must modify the Config.dat file to specify the data source to switch from one data source to another. Restart the IdeaBlade service after switching data sources.
If you want to have separate database instances accessible at the same time via an n-tier setup, you need to have separate n-tier server installations because a single n-tier server can only point to one database, and workstations will only connect to the database that the n-tier server points to.